Move get_auto_lims function to utils#281
Move get_auto_lims function to utils#281alejoe91 merged 1 commit intoSpikeInterface:mainfrom FrancescoNegri:refactoring/get-auto-lims
Conversation
|
Should I write some documentation for |
Yes please do, that would be brilliant, thanks!! This sounds like a good idea, although I don't know this area of the codebase well. My only question is whether |
|
I don't know if it will be used outside the context of plotting, but it should be at least agnostic with respect to the plotting backend. If, for instance, I want to plot something with |
|
Nice! Okay that makes sense, if it is more related to plotting I would consider a |
|
I was thinking that maybe the best thing is to add the |
@JoeZiminski @alejoe91 any thoughts about this? :) |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #281 +/- ##
=======================================
Coverage 88.91% 88.92%
=======================================
Files 10 10
Lines 1868 1869 +1
=======================================
+ Hits 1661 1662 +1
Misses 207 207 ☔ View full report in Codecov by Sentry. |
|
Hey @FrancescoNegri sorry for the delay here, I think Alessio was happy with the location on utils and I don't really know anything about this codebase so sounds good to me! If you still wanted to add the docstring for |
|
Sounds great, thanks @JoeZiminski! I have been quite busy lately, but I will try and open a new pull request for the |
get_auto_limscomputes the boundaries of the given probe. It relies exclusively on vanilla Python andnumpy. Theplottingnamespace, where the function is defined, importsmatplotlib, that might not always be available. Hence,get_auto_limsshould be independent onmatplotliband my suggestion is to move it toutils.